Medical device usage monitoring system and method

ABSTRACT

A method, computer program product, and computer system for determining that a user wears a wearable device during one or more time periods. A total amount of time that the user is wearing the wearable device during the one or more time periods may be tracked. The total amount of time that the user wears the wearable device during the one or more time periods may be transmitted to a computing device for display on a user interface.

RELATED CASES

This application is a continuation of U.S. Non-Provisional applicationSer. No. 16/925,652, filed on 10 Jul. 2020 which application claims thebenefit of U.S. Provisional Application No. 62/873,541, filed on 12 Jul.2019, the contents of which are herein incorporated by reference.

BACKGROUND

Generally, after a patient is diagnosed with a back problem (e.g.,idiopathic scoliosis), a doctor or other health processional mayprescribe a back brace. In order for it to significantly improve theposition of the spine, guidelines say the brace has to be worn a certainnumber of hours per day based on the patient's spinal curvature(commonly up to or exceeding eighteen hours a day). Patients must adhereto these guidelines to reap the full benefits of the back brace.

BRIEF SUMMARY OF DISCLOSURE

In one example implementation, a method, performed by one or morecomputing devices, may include but is not limited to determining that auser wears a wearable device during one or more time periods. A totalamount of time that the user is wearing the wearable device during theone or more time periods may be tracked. The total amount of time thatthe user wears the wearable device during the one or more time periodsmay be transmitted to a computing device for display on a userinterface.

One or more of the following example features may be included. The totalamount of time that the user wears the wearable device during the one ormore time periods may be transmitted manually. The total amount of timethat the user wears the wearable device during the one or more timeperiods may be transmitted automatically. A sensor connected to thewearable device may determine that the user wears the wearable deviceduring one or more time periods. The sensor may include at least one ofa capacitive sensor, a proximity sensor, a pressure sensor, atemperature sensor, and a motion sensor. The wearable device may be aback brace. The wearable device may include at least one of a kneebrace, an ankle brace, a sling, a removable cast, a posture device, anda post-surgical stabilization device.

In another example implementation, a computing system may include one ormore processors and one or more memories configured to performoperations that may include but are not limited to determining that auser wears a wearable device during one or more time periods. A totalamount of time that the user is wearing the wearable device during theone or more time periods may be tracked. The total amount of time thatthe user wears the wearable device during the one or more time periodsmay be transmitted to a computing device for display on a userinterface.

One or more of the following example features may be included. The totalamount of time that the user wears the wearable device during the one ormore time periods may be transmitted manually. The total amount of timethat the user wears the wearable device during the one or more timeperiods may be transmitted automatically. A sensor connected to thewearable device may determine that the user wears the wearable deviceduring one or more time periods. The sensor may include at least one ofa capacitive sensor, a proximity sensor, a pressure sensor, atemperature sensor, and a motion sensor. The wearable device may be aback brace. The wearable device may include at least one of a kneebrace, an ankle brace, a sling, a removable cast, a posture device, anda post-surgical stabilization device.

In another example implementation, a computer program product may resideon a computer readable storage medium having a plurality of instructionsstored thereon which, when executed across one or more processors, maycause at least a portion of the one or more processors to performoperations that may include but are not limited to determining that auser wears a wearable device during one or more time periods. A totalamount of time that the user is wearing the wearable device during theone or more time periods may be tracked. The total amount of time thatthe user wears the wearable device during the one or more time periodsmay be transmitted to a computing device for display on a userinterface.

One or more of the following example features may be included. The totalamount of time that the user wears the wearable device during the one ormore time periods may be transmitted manually. The total amount of timethat the user wears the wearable device during the one or more timeperiods may be transmitted automatically. A sensor connected to thewearable device may determine that the user wears the wearable deviceduring one or more time periods. The sensor may include at least one ofa capacitive sensor, a proximity sensor, a pressure sensor, atemperature sensor, and a motion sensor. The wearable device may be aback brace. The wearable device may include at least one of a kneebrace, an ankle brace, a sling, a removable cast, a posture device, anda post-surgical stabilization device.

The details of one or more example implementations are set forth in theaccompanying drawings and the description below. Other possible examplefeatures and/or possible example advantages will become apparent fromthe description, the drawings, and the claims. Some implementations maynot have those possible example features and/or possible exampleadvantages, and such possible example features and/or possible exampleadvantages may not necessarily be required of some implementations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example diagrammatic view of a tracking process coupled toan example distributed computing network according to one or moreexample implementations of the disclosure;

FIG. 2 is an example diagrammatic view of a client electronic device ofFIG. 1 according to one or more example implementations of thedisclosure;

FIG. 3 is an example flowchart of a tracking process according to one ormore example implementations of the disclosure;

FIG. 4 is an example flowchart of a tracking process according to one ormore example implementations of the disclosure

FIG. 5 is an example diagrammatic view of a back brace according to oneor more example implementations of the disclosure;

FIG. 6 is an example diagrammatic view of a user interface displayed bya tracking process according to one or more example implementations ofthe disclosure;

FIG. 7 is an example diagrammatic view of a user interface displayed bya tracking process according to one or more example implementations ofthe disclosure; and

FIG. 8 is an example diagrammatic view of a user interface displayed bya tracking process according to one or more example implementations ofthe disclosure.

Like reference symbols in the various drawings may indicate likeelements.

DETAILED DESCRIPTION

System Overview:

In some implementations, the present disclosure may be embodied as amethod, system, or computer program product. Accordingly, in someimplementations, the present disclosure may take the form of an entirelyhardware implementation, an entirely software implementation (includingfirmware, resident software, micro-code, etc.) or an implementationcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore, insome implementations, the present disclosure may take the form of acomputer program product on a computer-usable storage medium havingcomputer-usable program code embodied in the medium.

In some implementations, any suitable computer usable or computerreadable medium (or media) may be utilized. The computer readable mediummay be a computer readable signal medium or a computer readable storagemedium. The computer-usable, or computer-readable, storage medium(including a storage device associated with a computing device or clientelectronic device) may be, for example, but is not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, device, or any suitable combination ofthe foregoing. More specific examples (a non-exhaustive list) of thecomputer-readable medium may include the following: an electricalconnection having one or more wires, a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), anoptical fiber, a portable compact disc read-only memory (CD-ROM), anoptical storage device, a digital versatile disk (DVD), a static randomaccess memory (SRAM), a memory stick, a floppy disk, a mechanicallyencoded device such as punch-cards or raised structures in a groovehaving instructions recorded thereon, a media such as those supportingthe internet or an intranet, or a magnetic storage device. Note that thecomputer-usable or computer-readable medium could even be a suitablemedium upon which the program is stored, scanned, compiled, interpreted,or otherwise processed in a suitable manner, if necessary, and thenstored in a computer memory. In the context of the present disclosure, acomputer-usable or computer-readable, storage medium may be any tangiblemedium that can contain or store a program for use by or in connectionwith the instruction execution system, apparatus, or device.

In some implementations, a computer readable signal medium may include apropagated data signal with computer readable program code embodiedtherein, for example, in baseband or as part of a carrier wave. In someimplementations, such a propagated signal may take any of a variety offorms, including, but not limited to, electro-magnetic, optical, or anysuitable combination thereof. In some implementations, the computerreadable program code may be transmitted using any appropriate medium,including but not limited to the internet, wireline, optical fibercable, RF, etc. In some implementations, a computer readable signalmedium may be any computer readable medium that is not a computerreadable storage medium and that can communicate, propagate, ortransport a program for use by or in connection with an instructionexecution system, apparatus, or device.

In some implementations, computer program code for carrying outoperations of the present disclosure may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java®, Smalltalk, C++ or the like.Java® and all Java-based trademarks and logos are trademarks orregistered trademarks of Oracle and/or its affiliates. However, thecomputer program code for carrying out operations of the presentdisclosure may also be written in conventional procedural programminglanguages, such as the “C” programming language, PASCAL, or similarprogramming languages, as well as in scripting languages such asJavascript, PERL, or Python. The program code may execute entirely onthe user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough a local area network (LAN), a wide area network (WAN), a bodyarea network BAN), a personal area network (PAN), a metropolitan areanetwork (MAN), etc., or the connection may be made to an externalcomputer (for example, through the internet using an Internet ServiceProvider). In some implementations, electronic circuitry including, forexample, programmable logic circuitry, an application specificintegrated circuit (ASIC), field-programmable gate arrays (FPGAs) orother hardware accelerators, micro-controller units (MCUs), orprogrammable logic arrays (PLAs) may execute the computer readableprogram instructions/code by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present disclosure.

In some implementations, the flowchart and block diagrams in the figuresillustrate the architecture, functionality, and operation of possibleimplementations of apparatus (systems), methods and computer programproducts according to various implementations of the present disclosure.Each block in the flowchart and/or block diagrams, and combinations ofblocks in the flowchart and/or block diagrams, may represent a module,segment, or portion of code, which comprises one or more executablecomputer program instructions for implementing the specified logicalfunction(s)/act(s). These computer program instructions may be providedto a processor of a general purpose computer, special purpose computer,or other programmable data processing apparatus to produce a machine,such that the computer program instructions, which may execute via theprocessor of the computer or other programmable data processingapparatus, create the ability to implement one or more of thefunctions/acts specified in the flowchart and/or block diagram block orblocks or combinations thereof. It should be noted that, in someimplementations, the functions noted in the block(s) may occur out ofthe order noted in the figures (or combined or omitted). For example,two blocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved.

In some implementations, these computer program instructions may also bestored in a computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meanswhich implement the function/act specified in the flowchart and/or blockdiagram block or blocks or combinations thereof.

In some implementations, the computer program instructions may also beloaded onto a computer or other programmable data processing apparatusto cause a series of operational steps to be performed (not necessarilyin a particular order) on the computer or other programmable apparatusto produce a computer implemented process such that the instructionswhich execute on the computer or other programmable apparatus providesteps for implementing the functions/acts (not necessarily in aparticular order) specified in the flowchart and/or block diagram blockor blocks or combinations thereof.

Referring now to the example implementation of FIG. 1, there is showntracking process 10 that may reside on and may be executed by a computer(e.g., computer 12), which may be connected to a network (e.g., network14) (e.g., the internet or a local area network). Examples of computer12 (and/or one or more of the client electronic devices noted below) mayinclude, but are not limited to, a storage system (e.g., a NetworkAttached Storage (NAS) system, a Storage Area Network (SAN)), a personalcomputer(s), a laptop computer(s), mobile computing device(s), a servercomputer, a series of server computers, a mainframe computer(s), or acomputing cloud(s). A SAN may include one or more of the clientelectronic devices, including a RAID device and a NAS system. In someimplementations, each of the aforementioned may be generally describedas a computing device. In certain implementations, a computing devicemay be a physical or virtual device. In many implementations, acomputing device may be any device capable of performing operations,such as a dedicated processor, a portion of a processor, a virtualprocessor, a portion of a virtual processor, portion of a virtualdevice, or a virtual device. In some implementations, a processor may bea physical processor or a virtual processor. In some implementations, avirtual processor may correspond to one or more parts of one or morephysical processors. In some implementations, the instructions/logic maybe distributed and executed across one or more processors, virtual orphysical, to execute the instructions/logic. Computer 12 may execute anoperating system, for example, but not limited to, Microsoft® Windows®;Mac® OS X®; Red Hat® Linux®, Windows® Mobile, Chrome OS, Blackberry OS,Fire OS, or a custom operating system. (Microsoft and Windows areregistered trademarks of Microsoft Corporation in the United States,other countries or both; Mac and OS X are registered trademarks of AppleInc. in the United States, other countries or both; Red Hat is aregistered trademark of Red Hat Corporation in the United States, othercountries or both; and Linux is a registered trademark of Linus Torvaldsin the United States, other countries or both).

In some implementations, as will be discussed below in greater detail, atracking process, such as tracking process 10 of FIG. 1, may determinethat a user wears a wearable device during one or more time periods. Atotal amount of time that the user is wearing the wearable device duringthe one or more time periods may be tracked. The total amount of timethat the user wears the wearable device during the one or more timeperiods may be transmitted to a computing device for display on a userinterface.

In some implementations, the instruction sets and subroutines oftracking process 10, which may be stored on storage device, such asstorage device 16, coupled to computer 12, may be executed by one ormore processors and one or more memory architectures included withincomputer 12. In some implementations, storage device 16 may include butis not limited to: a hard disk drive; all forms of flash memory storagedevices; a tape drive; an optical drive; a RAID array (or other array);a random access memory (RAM); a read-only memory (ROM); or combinationthereof. In some implementations, storage device 16 may be organized asan extent, an extent pool, a RAID extent (e.g., an example 4D+1P R5,where the RAID extent may include, e.g., five storage device extentsthat may be allocated from, e.g., five different storage devices), amapped RAID (e.g., a collection of RAID extents), or combinationthereof.

In some implementations, network 14 may be connected to one or moresecondary networks (e.g., network 18), examples of which may include butare not limited to: a local area network; a wide area network or othertelecommunications network facility; or an intranet, for example. Thephrase “telecommunications network facility,” as used herein, may referto a facility configured to transmit, and/or receive transmissionsto/from one or more mobile client electronic devices (e.g., cellphones,etc.) as well as many others.

In some implementations, computer 12 may include a data store 20, suchas a database (e.g., relational database, object-oriented database,triplestore database, etc.) and may be located within any suitablememory location, such as storage device 16 coupled to computer 12. Insome implementations, data, metadata, information, etc. describedthroughout the present disclosure may be stored in the data store. Insome implementations, computer 12 may utilize any known databasemanagement system such as, but not limited to, DB2, in order to providemulti-user access to one or more databases, such as the above notedrelational database. In some implementations, the data store may also bea custom database, such as, for example, a flat file database or an XML,database. In some implementations, any other form(s) of a data storagestructure and/or organization may also be used. In some implementations,tracking process 10 may be a component of the data store, a standaloneapplication that interfaces with the above noted data store and/or anapplet/application that is accessed via client applications 22, 24, 26,28. In some implementations, the above noted data store may be, in wholeor in part, distributed in a cloud computing topology. In this way,computer 12 and storage device 16 may refer to multiple devices, whichmay also be distributed throughout the network.

In some implementations, computer 12 may execute a brace application(e.g., brace application 20), examples of which may include, but are notlimited to, e.g., a time tracking application, a calendar application, asensor recording application, or other application that allows for thetracking and maintaining of information related to a user wearing a backbrace (or other medical brace). An example of brace application 20 maybe the application provided by BraceTrack, LLC of Fort Lauderdale, Fla.However, it will be appreciated that any application and user interfacecapable of performing the present disclosure may also be used withoutdeparting from the scope of the present disclosure. As such, theapplication provided by BraceTrack should be taken as example only andnot to otherwise limit the scope of the present disclosure.

In some implementations, tracking process 10 and/or brace application 20may be accessed via one or more of client applications 22, 24, 26, 28.In some implementations, tracking process 10 may be a standaloneapplication, or may be an applet/application/script/extension that mayinteract with and/or be executed within brace application 20, acomponent of brace application 20, and/or one or more of clientapplications 22, 24, 26, 28. In some implementations, brace application20 may be a standalone application, or may be anapplet/application/script/extension that may interact with and/or beexecuted within tracking process 10, a component of tracking process 10,and/or one or more of client applications 22, 24, 26, 28. In someimplementations, one or more of client applications 22, 24, 26, 28 maybe a standalone application, or may be anapplet/application/script/extension that may interact with and/or beexecuted within and/or be a component of tracking process 10 and/orbrace application 20. Examples of client applications 22, 24, 26, 28 mayinclude, but are not limited to, e.g., a time tracking application, acalendar application, a sensor recording application, or otherapplication that allows for the tracking and maintaining of informationrelated to a user wearing a back brace (or other medical brace), a braceapplication, a standard and/or mobile web browser, an email application(e.g., an email client application), a textual and/or a graphical userinterface, a customized web browser, a plugin, an ApplicationProgramming Interface (API), or a custom application. The instructionsets and subroutines of client applications 22, 24, 26, 28, which may bestored on storage devices 30, 32, 34, 36, 30 a, 32 a, 34 a, 36 a,coupled to client electronic devices 38, 40, 42, 44 and/or brace 64, 66,68, 70, may be executed by one or more processors and one or more memoryarchitectures incorporated into client electronic devices 38, 40, 42, 44and/or brace 64, 66, 68, 70.

In some implementations, one or more of storage devices 30, 32, 34, 36,30 a, 32 a, 34 a, 36 a, may include but are not limited to: hard diskdrives; flash drives, tape drives; optical drives; RAID arrays; randomaccess memories (RAM); and read-only memories (ROM). Examples of clientelectronic devices 38, 40, 42, 44 (and/or computer 12) may include, butare not limited to, a personal computer (e.g., client electronic device38), a laptop computer (e.g., client electronic device 40), asmart/data-enabled, cellular phone (e.g., client electronic device 42),a notebook computer (e.g., client electronic device 44), a tablet, aserver, a television, a smart television, a smart speaker, an Internetof Things (IoT) device, a media (e.g., audio/video, photo, etc.)capturing and/or output device, an audio input and/or recording device(e.g., a handheld microphone, a lapel microphone, an embedded microphone(such as those embedded within eyeglasses, smart phones, tabletcomputers and/or watches, etc.), a brace (e.g., back brace), and adedicated network device. Additionally/alternatively, one or more ofclient electronic devices 38, 40, 42, 44 may include (or may be aseparate) monitoring device/sensor (e.g., also referred to herein asbrace 64, 66, 68, 70). Client electronic devices 38, 40, 42, 44 may eachexecute an operating system, examples of which may include but are notlimited to, Android™, Apple® iOS®, Mac® OS X®; Red Hat® Linux®, Windows®Mobile, Chrome OS, Blackberry OS, Fire OS, or a custom operating system.

In some implementations, one or more of client applications 22, 24, 26,28 may be configured to effectuate some or all of the functionality oftracking process 10 (and vice versa). Accordingly, in someimplementations, tracking process 10 may be a purely server-sideapplication, a purely client-side application, or a hybridserver-side/client-side application that is cooperatively executed byone or more of client applications 22, 24, 26, 28 and/or trackingprocess 10.

In some implementations, one or more of client applications 22, 24, 26,28 may be configured to effectuate some or all of the functionality ofbrace application 20 (and vice versa). Accordingly, in someimplementations, brace application 20 may be a purely server-sideapplication, a purely client-side application, or a hybridserver-side/client-side application that is cooperatively executed byone or more of client applications 22, 24, 26, 28 and/or braceapplication 20. As one or more of client applications 22, 24, 26, 28,tracking process 10, and brace application 20, taken singly or in anycombination, may effectuate some or all of the same functionality, anydescription of effectuating such functionality via one or more of clientapplications 22, 24, 26, 28, tracking process 10, brace application 20,or combination thereof, and any described interaction(s) between one ormore of client applications 22, 24, 26, 28, tracking process 10, braceapplication 20, or combination thereof to effectuate such functionality,should be taken as an example only and not to limit the scope of thedisclosure.

In some implementations, one or more of users 46, 48, 50, 52 and/or oneor more of brace 64, 66, 68, 70 may access computer 12 and trackingprocess 10 (e.g., using one or more of client electronic devices 38, 40,42, 44) directly through network 14 or through secondary network 18.Further, computer 12 may be connected to network 14 through secondarynetwork 18, as illustrated with phantom link line 54. Tracking process10 may include one or more user interfaces, such as browsers and textualor graphical user interfaces, through which users 46, 48, 50, 52 mayaccess tracking process 10 and/or brace 64, 66, 68, 70.

In some implementations, one or more of the various client electronicdevices and/or one or more of brace 64, 66, 68, 70 may be directly orindirectly coupled to network 14 (or network 18). For example, personalcomputer 38 and brace 64 are shown directly coupled to network 14 via ahardwired network connection. Further, notebook computer 44 and brace 70are shown directly coupled to network 18 via a hardwired networkconnection. Laptop computer 40 and brace 66 are shown wirelessly coupledto network 14 via wireless communication channels 56 a and 56 brespectively established between laptop computer 40 and wireless accesspoint (i.e., WAP) 58 and between brace 66 and WAP 58, which is showndirectly coupled to network 14. WAP 58 may be, for example, an IEEE802.11a, 802.11b, 802.11g, Wi-Fi®, RFID, and/or Bluetooth™ (includingBluetooth™ Low Energy) device that is capable of establishing wirelesscommunication channel 56 a between laptop computer 40 and WAP 58 andwireless communication channel 56 b between brace 66 and WAP 58.Additionally/alternatively, a brace (e.g., brace 66) may be directly(and/or wirelessly) coupled to a client electronic device (e.g., clientelectronic device 40) as illustrated with phantom link line 55. Thus,information may be communicated from a brace (e.g., brace 66) to aclient electronic device (e.g., client electronic device 40), where theinformation may be communicated, e.g., to computer 12 via, e.g., anetwork (e.g., network 14). Smart phone 42 and brace 68 are shownwirelessly coupled to network 14 via wireless communication channels 60a and 60 b respectively established between smart phone 42 and cellularnetwork/bridge 62 and brace 68 and cellular network/bridge 62, which isshown by example directly coupled to network 14.

In some implementations, some or all of the IEEE 802.11x specificationsmay use Ethernet protocol and carrier sense multiple access withcollision avoidance (i.e., CSMA/CA) for path sharing. The various802.11x specifications may use phase-shift keying (i.e., PSK) modulationor complementary code keying (i.e., CCK) modulation, for example.Bluetooth™ (including Bluetooth™ Low Energy) is a telecommunicationsindustry specification that allows, e.g., mobile phones, computers,smart phones, and other electronic devices (e.g., brace 64, 66, 68, 70)to be interconnected using a short-range wireless connection. Otherforms of interconnection (e.g., Near Field Communication (NFC)) may alsobe used.

In some implementations, various I/O requests (e.g., I/O request 15) maybe sent from, e.g., client applications 22, 24, 26, 28 and/or brace 64,66, 68, 70 to, e.g., computer 12 (and vice versa). Examples of I/Orequest 15 may include but are not limited to, data write requests(e.g., a request that content be written to computer 12) and data readrequests (e.g., a request that content be read from computer 12). Otherexamples of I/O request 15 may include sensor data transmitted betweenthe brace and computer 12, or other type of data indicating that a useris wearing the brace.

Referring also to the example implementation of FIG. 2, there is shown adiagrammatic view of client electronic device 38. While clientelectronic device 38 is shown in this figure, this is for examplepurposes only and is not intended to be a limitation of this disclosure,as other configurations are possible. Additionally, any computing devicecapable of executing, in whole or in part, tracking process 10 may besubstituted for client electronic device 38 (in whole or in part) withinFIG. 2, examples of which may include but are not limited to computer 12and/or one or more of client electronic devices 38, 40, 42, 44 and/orone or more of brace 64, 66, 68, 70.

In some implementations, client electronic device 38 may include aprocessor (e.g., microprocessor 200) configured to, e.g., process dataand execute the above-noted code/instruction sets and subroutines.Microprocessor 200 may be coupled via a storage adaptor to theabove-noted storage device(s) (e.g., storage device 30). An I/Ocontroller (e.g., I/O controller 202) may be configured to couplemicroprocessor 200 with various devices (e.g., via wired or wirelessconnection), such as keyboard 206, pointing/selecting device (e.g.,touchpad, touchscreen, mouse 208, etc.), custom device (e.g., device 215such as a sensor), USB ports, and printer ports. A display adaptor(e.g., display adaptor 210) may be configured to couple display 212(e.g., touchscreen monitor(s), plasma, CRT, or LCD monitor(s), etc.)with microprocessor 200, while network controller/adaptor 214 (e.g., anEthernet adaptor) may be configured to couple microprocessor 200 to theabove-noted network 14 (e.g., the Internet or a local area network).

Generally, after a patient is diagnosed with a back problem (e.g.,idiopathic scoliosis), a doctor or other health processional mayprescribe a back brace. In order for it to significantly improve theposition of the spine, guidelines say the brace has to be worn a certainnumber of hours per day based on the patient's spinal curvature(commonly up to or exceeding eighteen hours a day). Patients must adhereto these guidelines to reap the full benefits of the back brace. It isgenerally difficult to keep track of the hours that the patient wearsthe brace. Therefore, as will be discussed below, to help patients anddoctors easily, accurately, efficiently, and verifiably track the timeand “banked time” the brace is worn, the present disclosure may includea sensor that may be separate from a back brace, or included in the backbrace, that may track how long a user is wearing the brace. As will alsobe discussed below, the present disclosure may include an applicationthat may maintain an accurate log of how long the user is wearing thebrace (e.g., either by manual entry by the user or automatically byreceiving data from the brace sensor) which may be displayed to theuser.

As will be discussed below, tracking process 10 may at least help, e.g.,improve existing technological processes, necessarily rooted in computertechnology in order to overcome an example and non-limiting problemspecifically arising in the realm of patient adherence to wearing abrace, and being integrated into the practical application of monitoringand tracking such an adherence automatically and/or manually. It will beappreciated that the computer processes described throughout areintegrated into one or more practical applications, and when taken atleast as a whole are not considered to be well-understood, routine, andconventional functions.

The Tracking Process:

As discussed above and referring also at least to the exampleimplementations of FIGS. 3-8, tracking process 10 may determine 300 thata user wears a wearable device during one or more time periods. Trackingprocess 10 may track 302 a total amount of time that the user is wearingthe wearable device during the one or more time periods. Trackingprocess 10 may transmit 304 the total amount of time that the user wearsthe wearable device during the one or more time periods to a computingdevice for display on a user interface.

As noted above, after a patient is diagnosed with a back problem (e.g.,idiopathic scoliosis), a doctor or other health processional mayprescribe a back brace to be worn by the patient. In order for it tosignificantly improve the position of the spine, guidelines say thebrace has to be worn a certain number of hours per day based on thepatient's spinal curvature (commonly at least eighteen hours a day butother times/guidelines may be used). Patients must typically adhere tothese guidelines to reap the full benefits of the back brace, which maybe onerous to track.

As such, in some implementations, tracking process 10 may determine 300that a user wears a wearable device during one or more time periods. Forinstance, and referring at least to the example implementation of FIG.5, an example wearable device (e.g., back brace 500) is shown. As usedherein, the terms wearable device, back brace, and brace may be usedinterchangeably. As shown in FIG. 5 and discussed further below, backbrace 500 may include at least one sensor (e.g., sensor 502), a powersource 501 (e.g., battery or direct AC connection), a transceiver 503(e.g., Bluetooth Low Energy (BLE) System on Chip (SOC) transceiver), andmemory 505.

For example, in some implementations, a sensor connected to the wearabledevice (e.g., back brace 500) may determine 300 that the user wears (oris wearing) the wearable device during one or more time periods. Forinstance, as shown in FIG. 5, at least one sensor (e.g., sensor 502) maybe attached to or embedded within back brace 500. For example, in acommon back brace, sensor 502 may be located in the front of back brace500 (e.g., approximating the position of the user's belly button) andmay be of a thickness typical of back brace 500 or any other thicknesscapable of operating effectively. In some implementations, sensor 502may include at least one of a capacitive sensor, a proximity sensor, apressure sensor, a temperature sensor, and a motion sensor. For example,when sensor 502 is a pressure sensor, the pressure sensor may bepositioned anywhere on the inside of back brace 500 so as to be pressed(or sense sufficient pressure) when back brace 500 is worn. In theexample, when wearing back brace 500, the user would inherently applysufficient pressure or “press” upon the sensor with the user's body toprovide an indication signal to make a determination 300 that back brace500 is being worn. As another example, when sensor 502 is a temperaturesensor, the temperature sensor may be positioned anywhere on the insideof back brace 500 so as to detect temperature when back brace 500 isworn. In the example, when wearing back brace 500, the user would coversensor 502, thereby changing the current temperature detected by sensor502. In some implementations, sensor 502 may be based on a dual channelcapacitive proximity sensor (e.g., detects the presence or absence ofvirtually any object, such as the user wearing brace 500, regardless ofmaterial by utilizing the electrical property of capacitance and thechange of capacitance based on a change in the electrical field aroundthe active face of the sensor), as well as a proximity sensor (e.g.,detecting the presence or absence of an object, such as the user wearingbrace 500, using electromagnetic fields, light, and sound) which may beused to detect the wear state of the brace for a long period of time, orcombination conductance proximity sensor. Temperature sensing may beused to account for drift in capacitance due to temperature changes. Anon-limiting example of such a sensor is the AZD107 or IQS620/IQS620Asensor offered by Azoteq of Austin Tex. In some implementations, whentemperature is detected within a certain range (e.g., between 96 and 102degrees) this would provide an indication signal to make a determination300 that back brace 500 is being worn. As yet another example, whensensor 502 is a motion/movement sensor (e.g., accelerometer, gyroscope,GPS, etc.), this sensor may be positioned anywhere on the inside and/oroutside of back brace 500 so as to detect movement when back brace 500is worn. In the example, when wearing back brace 500, the user may movearound, causing sensor 502 to detect this movement to provide anindication signal to make a determination 300 that back brace 500 isbeing worn.

In some implementations, to help increase accuracy, any combination andany number of the above-noted sensors may be used. For instance, onlyone sensor (e.g., temperature) determining that back brace 500 is beingworn may not be sufficient to make a final determination that back brace500 is being worn (e.g., if it is already warm in the room or the braceis in the sunlight), whereas two or more sensors (e.g., temperature andpressure) essentially simultaneously determining that back brace 500 isbeing worn may be sufficient to make a final determination that backbrace 500 is being worn. As another example, only one pressure sensordetermining that back brace 500 is being worn may not be sufficient tomake a final determination that back brace 500 is being worn (e.g., ifsomething is accidentally resting on top of the pressure sensor),whereas two or more pressure sensors determining that back brace 500 isbeing worn may be sufficient to make a final determination that backbrace 500 is being worn.

In some implementations, tracking process 10 may track 302 (e.g.,monitor) a total amount of time that the user is wearing the wearabledevice during the one or more time periods. For instance, in someimplementations, the on/off state of any of the above sensors may becaptured over, e.g., I²C with a Bluetooth Low Energy (BLE) System onChip (SOC) (e.g., via transceiver 503) or Wi-Fi, etc. The BLE SOC maycontain a radio to connect with a computing device (e.g., mobilephone/tablet, etc. and/or a microprocessor) to process the data streamfrom the sensor. The module may also contain memory 505 (e.g., flashmemory) to temporarily store sensor readings along with a timestamp.Sensor data may be temporarily stored in the module for situations wherethe receiving mobile device is either not within transmission proximityof the sensor or is turned off. The BLE module may advertise itspresence continuously or periodically. The computing device may pick upthose advertising signals and connect to sensor 502 using, e.g.,Bluetooth Low Energy. Once a connection is established, the computingdevice may request on/off events along with the timestamp from sensor502.

In some implementations, using the above-noted sensor(s) 502 todetermine whether or not the user is wearing back brace 500, trackingprocess 10 may (e.g., using the above-noted timestamp or otherwise)track 302 (e.g., monitor) how long the user is wearing back brace 500for a particular time period (e.g., one day, one week, one month, etc.).For example, assume that sensor 502 is used to determine that the useris wearing back brace 500 for 8 hours on Monday (e.g., 4 hours from 10am to 2 pm and then 4 hours from 4 pm to 8 pm). In the example, trackingprocess 10 may track 302 that the user has worn back brace 500 for 8hours on Monday. As another example, assume that sensor 502 is used todetermine that the user is wearing back brace 500 for 8 hours on Monday,and 6 hours on Tuesday of the same week. In the example, trackingprocess 10 may track 302 that the user has worn back brace 500 for 8hours on Monday and 6 hours on Tuesday of the same week.

In some implementations, tracking process 10 may transmit 304 the totalamount of time that the user wears the wearable device during the one ormore time periods to a computing device for display on a user interface.For example, as will be discussed in greater detail below, the totalamount of time where the user was determined to have worn back brace 500(e.g., 8 hours on Monday and/or 6 hours on Tuesday) may be transmitted304 to a computing device (e.g., client electronic device 42 via clientapplication 26 and/or to computer 12 which may then be transmitted toclient electronic device 42) to log and display this amount of time forthe user (or medical professional) on a user interface (e.g., userinterface 508). In some implementations, the data may be transmitted 304wirelessly (as discussed above) and/or the data may be transmitted 304via a wired connection (as discussed above). While client electronicdevice 42 may be a mobile device (e.g., smart phone), in someimplementations, the client electronic device may be a wired device thatis wired directly to sensor 502. For instance, as shown in FIG. 5,client electronic device 504 is shown connected to back brace 500 viawired connection 506. Client electronic device 504 may include a userinterface capable of displaying the above-noted amount of time backbrace 500 is worn or time remaining to be worn, or any other relevantinformation, such as those discussed below with FIGS. 6-8.

In some implementations, the total amount of time that the user wearsthe wearable device during the one or more time periods may betransmitted 304 automatically. For example, as will be discussed furtherbelow, the total amount of time that the user wears back brace 500 maybe transmitted in real-time (e.g., in example intervals of 1-2 secondsor minutes) as the user is wearing back brace 500. In someimplementations, the total amount of time that the user wears back brace500 may be transmitted after sensor 502 determines that the user is nolonger wearing back brace 500, which may help save resources (e.g.,battery life, processing resources, storage space, bandwidth, etc.) ofback brace 500 and/or client electronic device 42. In someimplementations, the total amount of time may be verified by the userprior to transmitting and/or after transmitting.

In some implementations, the total amount of time that the user wearsthe wearable device during the one or more time periods may betransmitted 304 manually. For example, as will be discussed furtherbelow, the total amount of time that the user wears back brace 500 maybe transmitted manually. For instance, the user may manually uploadand/or enter the hours/minutes into client electronic device 42 via auser interface of client application 26. In some implementations, manualentry need not require use of sensor 502, and client electronic device504 may include a timer that the user may be manually started andstopped by the user to determine how long back brace 500 has been worn.In some implementations, manual entry may still use sensor 502, whereclient electronic device 504 may include a timer that may start and stopdepending on the use of the sensor to determine whether back brace 500is being worn, which may be verified by the user and then added manually(or added automatically without verification).

Additionally, as also discussed above and referring also at least to theexample implementations of FIGS. 4-8, tracking process 10 may receive400, by a computing device, a total amount of time that a user wears awearable device during one or more time periods. Tracking process 10 maycompare 402 the total amount of time that the user wears the wearabledevice during the one or more time periods to a threshold amount of timefor the one or more time periods. Tracking process 10 may display 404 ona user interface a remaining amount of time for the user to wear thewearable device during the one or more time periods based upon, at leastin part, comparing the total amount of time that the user wears thewearable device during the one or more time periods to the thresholdamount of time.

In some implementations, tracking process 10 may receive 400, by acomputing device, a total amount of time that a user wears a wearabledevice during one or more time periods. For instance, one or moreimplementations of the above-described back brace 500 may be used totransmit the above-noted total amount of time that the user wears backbrace 500, which may be received 400 by tracking process 10 (e.g., viasensor 502 connected to the wearable device, wherein the sensor mayinclude at least one of a pressure sensor, a temperature sensor, and amotion sensor). As described above, the total amount of time where theuser was determined to have worn back brace 500 (e.g., 8 hours on Mondayand/or 6 hours on Tuesday) may be transmitted 304 to and received 400 bya computing device (e.g., client electronic device 42 via clientapplication 26 and/or to computer 12 which may then be transmitted toand received 400 by client electronic device 42) to log and display forthe user (or medical professional) on a user interface this amount oftime (discussed below).

As also noted above, the total amount of time that the user wears thewearable device during the one or more time periods may be received 400automatically, and in some implementations the total amount of time thatthe user wears the wearable device during the one or more time periodsmay be received 400 manually. For instance, and referring at least tothe example implementation of FIG. 6, an example user interface 600(e.g., of tracking process 10 via client application 26 of clientelectronic device 42) is shown. In the example, an “Add Time” icon 602may be selected by the user using any known technique (e.g., touchscreen). By selecting this example icon 602, the user may manuallyupload and/or enter the hours/minutes into client electronic device 42via user interface 600 of client application 26. In someimplementations, manual entry need not require use of sensor 502, andclient electronic device 504 may include a timer that the user maymanually start (e.g., via icon 604) and stop (e.g., via icon 606) todetermine how long back brace 500 has been worn (e.g., for the currentday). In some implementations, manual entry may still use sensor 502,where client electronic device 504 may include a timer that may startand stop depending on the use of the sensor to determine whether backbrace 500 is being worn, which may be verified by the user and thenadded manually (or added automatically without verification).

In some implementations, tracking process 10 may compare 402 the totalamount of time that the user wears the wearable device during the one ormore time periods to a threshold amount of time for the one or more timeperiods, and in some implementations, tracking process 10 may display404 on a user interface a remaining amount of time for the user to wearthe wearable device during the one or more time periods based upon, atleast in part, comparing the total amount of time that the user wearsthe wearable device during the one or more time periods to the thresholdamount of time. For instance, assume for example purposes only that theuser is required to wear back brace 500 for 18 hours (as shown in FIG.6). In the example, further assume that the user, for the current day,has worn back brace 500 for 8 hours and 1 minute (as also shown in FIG.6). Tracking process 10 may compare 402 that total amount of time (8hours and 1 minute) to the required (threshold) amount of time for thatsame day (18 hours). As a result, tracking process 10 may display 404(e.g., via user interface 600) the remaining amount of time that theuser should wear back brace 500 (e.g., 9 hours and 59 minutes) to meetthe above-noted guidelines. In some implementations, the thresholdamount of time may be changed in the user's profile (e.g., via profileicon 608), which may include other options as well (e.g., entering theuser's name, device pairing options or other connectivity options,etc.).

In some implementations, displaying 404 on the user interface theremaining amount of time for the user to wear the wearable device duringthe one or more time periods may include displaying 406 a surplus amountof time above the threshold amount of time that the user wears thewearable device during the one or more time periods. For instance, andreferring to the example implementation of FIG. 7, an example userinterface (e.g., user interface 700 of tracking process 10 via clientapplication 26 of client electronic device 42) is shown. In the example,tracking process 10 may display 406 a surplus amount of time that isabove the threshold amount of time that the user is required to wearback brace 500. For instance, and continuing with the above example,assume for example purposes only that the threshold amount of time for aparticular period (e.g., a single day) is 18 hours, and further assumethat tracking process 10 has only received data indicating that the userhas worn back brace 500 for 8 hours and 1 minute for that same day. Inthe example, there would be 0 surplus or “banked” hours (as shown inFIG. 7), as the user has not even worn back brace 500 long enough tomeet the threshold of 18 hours, let alone worn back brace 500 longerthan the threshold of 18 hours. However, now assume that trackingprocess 10 has received data indicating that the user has worn backbrace 500 for 19 hours and 1 minute for that same day. In the example,there would be 1 hour and 1 minute surplus or “banked” hours shown inFIG. 7, as the user has worn back brace 500 for 1 hour and 1 minutelonger than the threshold of 18 hours. In some implementations,selecting the example “history” icon 712 may display the surplus amountof time, as well as other historical usage data (e.g., history for anygiven date in the user's brace tracking history). In someimplementations, user interface 700 may enable the user to export theuser's history of brace time worn and banked for, e.g., the trailingweek, month, and year along with daypart trends (e.g., via a PDF (orother format) email, text, etc.) Daypart trends may include, e.g., thetypical hours the brace is being worn so the user may visualize patternsby time of day.

It will be appreciated that while the surplus hours is displayed for aparticular day, other time periods may also be used when displaying 406the surplus. For example, now assume that tracking process 10 hasreceived data indicating that the user has worn back brace 500 for 127hours and 1 minute for the week. In the example, there would be 1 hourand 1 minute surplus or “banked” hours, as the user has worn back brace500 for 1 hour and 1 minute longer than the threshold of 126 hours forthe week (i.e., 18 hours a day×7 days=126 hours). Other time periodsthat may be used include months, years, etc., which may be viewed inuser interface 700 by selecting the appropriate icon (e.g., Trailingweek icon 702, Trailing month icon 704, Trailing year icon 706, Trendsicon 708, etc., which may be viewed in any form, such as the graph 710,and which may also show the deficit amount of time needed to wear backbrace 500 to meet the threshold). As such, the use of a single day asthe time period should be taken as example only and not to otherwiselimit the scope of the present disclosure.

In some implementations, and referring to the example implementation ofFIG. 8, an example user interface (e.g., user interface 800 of trackingprocess 10 via client application 26 of client electronic device 42) isshown. In the example, information pertaining to the total amount oftime the user has worn back brace 500 may be displayed by tackingprocess 10 and viewed by the user in calendar form (e.g., by selectingthe example “calendar” icon 804). For instance, the user may select thecurrent day (e.g., 9 Jun. 2020), which may display the currentinformation for that day (e.g., 8 hours and 1 minute having worn backbrace 500), how many surplus hours have been banked for that day, aswell as how many surplus hours have been applied (as will be discussedfurther below). In some implementations, tracking process 10 may displayall available data up to the selected day (e.g., 1 Jun. 2020-9 Jun.2020), and in other implementations, the user may manually select whichdays (or months, years, etc.) to include when displaying the availabledata.

In some implementations, displaying 404 on the user interface theremaining amount of time for the user to wear the wearable device duringthe one or more time periods may include applying 408 the surplus amountof time above the threshold amount of time to the remaining amount oftime for the user to wear the wearable device during the one or moretime periods. For instance, assume that tracking process 10 has receiveddata indicating that the user has worn back brace 500 for 19 hours and 1minute for a particular day (e.g., 8 Jun. 2020). In the example, therewould be 1 hour and 1 minute surplus or “banked” hours shown in FIG. 7,as the user has worn back brace 500 for 1 hour and 1 minute longer thanthe threshold of 18 hours. Now assume that tracking process 10 had alsoreceived data indicating that the user has worn back brace 500 for 17hours and 1 minute for the prior day (e.g., 7 Jun. 2020), leaving a 59minute deficiency for that prior day. In the example, tracking process10 may apply 408 the surplus (or “banked”) time of 59 minutes from 8Jun. 2020 to the 59 minute deficiency of 7 Jun. 2020, resulting in theuser meeting the 18 hour quota each day for two days.

In the example, the total amount of banked time that has been appliedmay be displayed on any of the example user interfaces described above.In some implementations, the total amount of banked time that has beenapplied may be applied automatically by tracking process 10 and/or maybe applied manually by tracking process 10 receiving an input from theuser (e.g., via example “Apply Banked Time” icon 802) to specificallyapply any portion of banked time to any particular day, week, month,etc.

While the description below describes a wearable device as a back brace,it will be appreciated that the wearable device may include other typesof wearable devices without departing from the scope of the presentdisclosure. For example, while in some implementations, the wearabledevice may be a back brace, in some implementations, the wearable devicemay include at least one of a knee brace (e.g., for MCL/ACL injuries andfor preventive knee braces used commonly in football and contactsports), an ankle brace, a sling (e.g., hamstring or shoulder sling), aremovable cast, a posture device, a post-surgical stabilization device,or any other type of wearable device. As such, the use of a back braceshould be taken as example only and not to otherwise limit the scope ofthe present disclosure.

It will be appreciated that tracking process 10, as shown in FIGS. 3 and4 and also discussed throughout, may be used separately or combined inany combination (e.g., as a brace to collect data, as an application toculminate and display the data, as a brace to collect data that thentransmits the data to the application to culminate and display the data,or a single apparatus capable of collecting and culminating data fordisplay, etc.). As such, the use of a separate device (e.g., brace withsensor) and a separate application should be taken as example only andnot to otherwise limit the scope of the present disclosure.

The terminology used herein is for the purpose of describing particularimplementations only and is not intended to be limiting of thedisclosure. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. As used herein, the language “at least one of A, B,and C” (and the like) should be interpreted as covering only A, only B,only C, or any combination of the three, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps (notnecessarily in a particular order), operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps (not necessarily in a particular order),operations, elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents (e.g., ofall means or step plus function elements) that may be in the claimsbelow are intended to include any structure, material, or act forperforming the function in combination with other claimed elements asspecifically claimed. The description of the present disclosure has beenpresented for purposes of illustration and description, but is notintended to be exhaustive or limited to the disclosure in the formdisclosed. Many modifications, variations, substitutions, and anycombinations thereof will be apparent to those of ordinary skill in theart without departing from the scope and spirit of the disclosure. Theimplementation(s) were chosen and described in order to explain theprinciples of the disclosure and the practical application, and toenable others of ordinary skill in the art to understand the disclosurefor various implementation(s) with various modifications and/or anycombinations of implementation(s) as are suited to the particular usecontemplated.

Having thus described the disclosure of the present application indetail and by reference to implementation(s) thereof, it will beapparent that modifications, variations, and any combinations ofimplementation(s) (including any modifications, variations,substitutions, and combinations thereof) are possible without departingfrom the scope of the disclosure defined in the appended claims.

What is claimed is:
 1. A computer-implemented method comprising:determining that a user wears a wearable device during a plurality oftime periods of equal duration; tracking a total amount of time that theuser is wearing the wearable device during the plurality of timeperiods; transmitting to a computing device the total amount of timethat the user wears the wearable device during each of the plurality oftime periods for display on a user interface; comparing the total amountof time that the user wears the wearable device during each of theplurality of time periods to a threshold amount of time for each of theplurality of time periods; and displaying on the user interface aremaining amount of time for the user to wear the wearable device duringeach of the plurality of time periods based upon, at least in part,comparing the total amount of time that the user wears the wearabledevice during each of the plurality of time periods to the thresholdamount of time for each of the plurality of time periods, whereindisplaying on the user interface the remaining amount of time for theuser to wear the wearable device during each of the plurality of timeperiods includes displaying a surplus amount of time above the thresholdamount of time for each of the plurality of time periods that the userwears the wearable device during each of the plurality of time periods,and wherein displaying on the user interface the remaining amount oftime for the user to wear the wearable device during each of theplurality of time periods further includes applying at least a portionof the surplus amount of time above the threshold amount of time foreach of the plurality of time periods to a past time period of theplurality of time periods that the user wore the wearable device belowthe threshold amount of time, wherein the past time period of theplurality of time periods that the user wore the wearable device belowthe threshold amount of time is a selection received from the user. 2.The computer-implemented method of claim 1 wherein the total amount oftime that the user wears the wearable device during each of theplurality of time periods is transmitted at least one of manually andautomatically.
 3. The computer-implemented method of claim 1 furthercomprising: applying at least the portion of the surplus amount of timeto the past time period based upon, at least in part, receiving theselection from the user of the past time period.
 4. Thecomputer-implemented method of claim 1 wherein a sensor connected to thewearable device determines that the user wears the wearable deviceduring each of the plurality of time periods.
 5. Thecomputer-implemented method of claim 4 wherein the sensor includes atleast one of a capacitive sensor, a proximity sensor, a pressure sensor,a temperature sensor, and a motion sensor.
 6. The computer-implementedmethod of claim 1 wherein the wearable device is a back brace.
 7. Thecomputer-implemented method of claim 1 wherein the wearable deviceincludes at least one of a knee brace, an ankle brace, a sling, aremovable cast, a posture device, and a post-surgical stabilizationdevice.
 8. A computer program product residing on a computer readablestorage medium having a plurality of instructions stored thereon which,when executed across one or more processors, causes at least a portionof the one or more processors to perform operations comprising:determining that a user wears a wearable device during a plurality oftime periods of equal duration; tracking a total amount of time that theuser is wearing the wearable device during the plurality of timeperiods; transmitting to a computing device the total amount of timethat the user wears the wearable device during each of the plurality oftime periods for display on a user interface; comparing the total amountof time that the user wears the wearable device during each of theplurality of time periods to a threshold amount of time for each of theplurality of time periods; and displaying on the user interface aremaining amount of time for the user to wear the wearable device duringeach of the plurality of time periods based upon, at least in part,comparing the total amount of time that the user wears the wearabledevice during each of the plurality of time periods to the thresholdamount of time for each of the plurality of time periods, whereindisplaying on the user interface the remaining amount of time for theuser to wear the wearable device during each of the plurality of timeperiods includes displaying a surplus amount of time above the thresholdamount of time for each of the plurality of time periods that the userwears the wearable device during each of the plurality of time periods,and wherein displaying on the user interface the remaining amount oftime for the user to wear the wearable device during each of theplurality of time periods further includes applying at least a portionof the surplus amount of time above the threshold amount of time foreach of the plurality of time periods to a past time period of theplurality of time periods that the user wore the wearable device belowthe threshold amount of time, wherein the past time period of theplurality of time periods that the user wore the wearable device belowthe threshold amount of time is a selection received from the user. 9.The computer program product of claim 8 wherein the total amount of timethat the user wears the wearable device during each of the plurality oftime periods is transmitted at least one of manually and automatically.10. The computer program product of claim 8 wherein the operationsfurther comprise: applying at least the portion of the surplus amount oftime to the past time period based upon, at least in part, receiving theselection from the user of the past time period.
 11. The computerprogram product of claim 8 wherein a sensor connected to the wearabledevice determines that the user wears the wearable device during each ofthe plurality of time periods.
 12. The computer program product of claim11 wherein the sensor includes at least one of a capacitive sensor, aproximity sensor, a pressure sensor, a temperature sensor, and a motionsensor.
 13. The computer program product of claim 8 wherein the wearabledevice is a back brace.
 14. The computer program product of claim 8wherein the wearable device includes at least one of a knee brace, anankle brace, a sling, a removable cast, a posture device, and apost-surgical stabilization device.
 15. A computing system including oneor more processors and one or more memories configured to performoperations comprising: determining that a user wears a wearable deviceduring a plurality of time periods of equal duration; tracking a totalamount of time that the user is wearing the wearable device during theplurality of time periods; transmitting to a computing device the totalamount of time that the user wears the wearable device during each ofthe plurality of time periods for display on a user interface; comparingthe total amount of time that the user wears the wearable device duringeach of the plurality of time periods to a threshold amount of time foreach of the plurality of time periods; and displaying on the userinterface a remaining amount of time for the user to wear the wearabledevice during each of the plurality of time periods based upon, at leastin part, comparing the total amount of time that the user wears thewearable device during each of the plurality of time periods to thethreshold amount of time for each of the plurality of time periods,wherein displaying on the user interface the remaining amount of timefor the user to wear the wearable device during each of the plurality oftime periods includes displaying a surplus amount of time above thethreshold amount of time for each of the plurality of time periods thatthe user wears the wearable device during each of the plurality of timeperiods, and wherein displaying on the user interface the remainingamount of time for the user to wear the wearable device during each ofthe plurality of time periods further includes applying at least aportion of the surplus amount of time above the threshold amount of timefor each of the plurality of time periods to a past time period of theplurality of time periods that the user wore the wearable device belowthe threshold amount of time, wherein the past time period of theplurality of time periods that the user wore the wearable device belowthe threshold amount of time is a selection received from the user. 16.The computing system of claim 15 wherein the total amount of time thatthe user wears the wearable device during each of the plurality of timeperiods is transmitted at least one of manually and automatically. 17.The computing system of claim 15 wherein the operations furthercomprise: applying at least the portion of the surplus amount of time tothe past time period based upon, at least in part, receiving theselection from the user of the past time period.
 18. The computingsystem of claim 15 wherein a sensor connected to the wearable devicedetermines that the user wears the wearable device during each of theplurality of time periods.
 19. The computing system of claim 18 whereinthe sensor includes at least one of a capacitive sensor, a proximitysensor, a pressure sensor, a temperature sensor, and a motion sensor.20. The computing system of claim 15 wherein the wearable device is aback brace.
 21. The computing system of claim 15 wherein the wearabledevice includes at least one of a knee brace, an ankle brace, a sling, aremovable cast, a posture device, and a post-surgical stabilizationdevice.